Google Git
Sign in
chromium / chromiumos / platform / touchpad-tests / 69ad8e106fee1a643aeb3c1c652c200975267272
commit69ad8e106fee1a643aeb3c1c652c200975267272[log] [tgz]
authorHarry Cutts <hcutts@chromium.org>Fri Oct 25 14:17:39 2024
committerChromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Oct 25 16:43:38 2024
tree1adecdd95b1356fd7add6ad2f47ebf798ff500be
parent5a3881cad014edc124d5b3dc8ede0bfb3ed0dd28 [diff]
README.md: update "Setting up" instructions The developer guide has moved, and ~/chromiumos inside the chroot is now a symlink to /mnt/host/source. Using the symlink is deprecated, if I recall correctly. BUG=None TEST=Check gitiles rendering Change-Id: I1414ffb67425c8e59b0410b309172d46293b6e95 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/touchpad-tests/+/5965105 Tested-by: Harry Cutts <hcutts@chromium.org> Auto-Submit: Harry Cutts <hcutts@chromium.org> Reviewed-by: Sean O'Brien <seobrien@chromium.org> Commit-Queue: Sean O'Brien <seobrien@chromium.org>
1 file changed
tree: 1adecdd95b1356fd7add6ad2f47ebf798ff500be
  1. framework/
  2. tests/
  3. .gitignore
  4. DIR_METADATA
  5. Makefile
  6. OWNERS
  7. README.md
  8. touchtests
  9. touchtests.template
  10. unblocked_terms.txt
README.md

Touch tests

Introduction

This repository contains automated tests for Chromium OS's Gestures library. Each test has a log of evdev events which are replayed, a properties file containing gesture properties to set while the Gestures library runs, and a Python function which verifies the output and returns a test score.

Setting up

Assuming that you've followed the developer guide, simply enter the SDK chroot using the cros_sdk command, then run the following inside:

(inside) $ cd /mnt/host/source/src/platform/touchpad-tests $ sudo make setup-in-place

Running tests

To run all tests, simply run touchtests. To run one or more specific tests, you can pass a test name or a glob:

(inside) $ touchtests atlas-1.0/fat-thumb-fail $ touchtests atlas-1.0/palm-while-typing*

Each test will return a status, with the following meanings:

  • success: the test succeeded, with the given score out of 1.
  • failure: the test failed.
  • error: an error occurred while running the test, so the behavior of the gestures library couldn't be evaluated.
  • incomplete: (baseline tests only) the evdev log for this platform hasn't been created.

Checking for regressions

The --out (or -o) switch creates a report file that future runs can be compared against with the --ref (or -r) switch:

(inside) $ touchtests --out baseline.json # (cause some regressions) $ touchtests --ref baseline.json

The output table will contain a delta column that indicates any regressions or improvements, and an error message will be shown if regressions exist.